home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
dev
/
www_talk.930
/
000120_jfg@dxcern.cern.ch _Mon Jun 8 17:34:55 1992.msg
< prev
next >
Wrap
Internet Message Format
|
1994-01-24
|
1KB
Return-Path: <jfg@dxcern.cern.ch>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA11440; Mon, 8 Jun 92 17:34:55 MET DST
Received: by dxmint.cern.ch (dxcern) (5.57/3.14)
id AA01254; Mon, 8 Jun 92 17:32:28 +0200
Received: by dxcern.cern.ch (5.57/Ultrix3.0-C)
id AA21936; Mon, 8 Jun 92 17:32:23 +0200
Date: Mon, 8 Jun 92 17:32:23 +0200
From: jfg@dxcern.cern.ch (Jean Francois Groff)
Message-Id: <9206081532.AA21936@dxcern.cern.ch>
To: Dan Connolly <connolly@pixel.convex.com>
Cc: www-talk@nxoc01.cern.ch
Subject: Re: overkill on portability macros
References: <9206070615.AA15478@pixel.convex.com>
> But ANSI C and PCC share syntax for _defining_ functions.
> The preprocessor dancing is necessary for _declaring_ functions
> like so:
>
> int foo __ARGS__((int x, int y, int z));
>
> but in the .c files, you can just do the usual
>
> int foo(x,y,z)
> int x;
> int y;
> int z;
True, but in the latter case you don't get any type checking of the
parameters in functions that happen NOT to be declared before their
definition. I agree that the syntax with extra commas is ugly, though,
but there was no better way.
JF